ALTER DATABASE
ALTER DATABASE — Change a Database
Synopsis
ALTER DATABASE name [ [ WITH ] option [ ... ] ]
where option can be:
ALLOW_CONNECTIONS allowconn
CONNECTION LIMIT connlimit
IS_TEMPLATE istemplate
ALTER DATABASE name RENAME TO new_name
ALTER DATABASE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
ALTER DATABASE name SET TABLESPACE new_tablespace
ALTER DATABASE name SET configuration_parameter { TO | = } { value | DEFAULT }
ALTER DATABASE name SET configuration_parameter FROM CURRENT
ALTER DATABASE name RESET configuration_parameter
ALTER DATABASE name RESET ALL
Description
ALTER DATABASE changes the attributes of a database.
The first form changes certain per-database settings (see below for details). Only the database owner or a superuser can change these settings.
The second form changes the name of the database. Only the database owner or a superuser can rename a database; non-superuser owners must also have the CREATEDB privilege. The current database cannot be renamed (if you need to do this, connect to a different database).
The third form changes the owner of the database. To change the owner, you must own the database and also be a direct or indirect member of the new owning role, and you must have the CREATEDB privilege (note that a superuser automatically has all these privileges).
The fourth form changes the default tablespace of the database. Only the database owner or a superuser can do this; you must also have the CREATE privilege on the new tablespace. This command physically moves any tables or indexes located in the database's old default tablespace to the new tablespace. The new default tablespace must be empty for this database, and no one can be connected to the database. Tables and indexes in non-default tablespaces are not affected.
The remaining forms change the session default value for a runtime configuration variable for a Halo database. Whenever a new session is subsequently started in that database, the specified value becomes the session default. Database-specific defaults override settings that appear in postgresql.conf. Only the database owner or a superuser can change the session defaults for a database. Some variables cannot be set in this way, or can only be set by a superuser.
Parameters
name
The name of the database whose attributes are to be modified.
allowconn
If false, no one can connect to this database.
connlimit
How many concurrent connections can be established to this database. -1 means no limit.
istemplate
If true, any user with the CREATEDB privilege can clone this database. If false, only superusers or the owner of the database can clone it.
new_name
The new name of the database.
new_owner
The new owner of the database.
new_tablespace
The new default tablespace for the database.
This form of the command cannot be executed inside a transaction block.
configuration_parameter
value
Sets the session default value of the specified configuration parameter for this database to the given value. If value is DEFAULT, or equivalently if RESET is used, the database-specific setting is removed, so the system-wide default setting will be inherited in new sessions. Use RESET ALL to clear all database-specific settings. SET FROM CURRENT saves the session's current parameter value as the database-specific value.
Notes
It is also possible to bind a session's default to a specific role rather than a database; see ALTER ROLE. Role-specific settings override database-specific ones if there is a conflict.
Examples
# To disable index scans by default in the database test:
ALTER DATABASE test SET enable_indexscan TO off;